@T4rk1n Should I resubmit a PR for this feature to adapt to the latest version of Dash? This feature is very useful for those who want to quickly load static resources such as js on demand in a Dash application. For example, when building an online spreadsheet feature based on Univer in Dash, there are requirements for the loading order of relevant js dependencies. By adding the assets_path_ignore parameter, it is convenient to ensure that the js in the relevant static file directory will not be automatically loaded in a disorderly manner in advance during application initialization.

@T4rk1n Should I resubmit a PR for this feature to adapt to the latest version of Dash? This feature is very useful for those who want to quickly load static resources such as js on demand in a Dash application. For example, when building an online spreadsheet feature based on Univer in Dash, there are requirements for the loading order of relevant js dependencies. By adding the assets_path_ignore parameter, it is convenient to ensure that the js in the relevant static file directory will not be automatically loaded in a disorderly manner in advance during application initialization.

Yes, I want to include this in next release 3.1, up to you if you want to resolve the conflicts in this PR or a new one.

Look like the format check failed:

ERROR: "private::lint.black" exited with 1.

I changed the pre-commit hook to only lint staged files and should runs almost instantly for these cases now.

Look like the format check failed:

ERROR: "private::lint.black" exited with 1.

I changed the pre-commit hook to only lint staged files and should runs almost instantly for these cases now.

I can't figure out exactly what caused the code format check to fail 😢, I've used ruff to format related .py files.

Look like the format check failed:

ERROR: "private::lint.black" exited with 1.

I changed the pre-commit hook to only lint staged files and should runs almost instantly for these cases now.

I can't figure out exactly what caused the code format check to fail 😢, I've used ruff to format related .py files.

That is because we use black not ruff 😆

Look like the format check failed:

ERROR: "private::lint.black" exited with 1.

I changed the pre-commit hook to only lint staged files and should runs almost instantly for these cases now.

I can't figure out exactly what caused the code format check to fail 😢, I've used ruff to format related .py files.

That is because we use black not ruff 😆

Yes, I used to think that ruff was 100% compatible with the black standard 😣. After executing npm run format, the relevant lint tests have passed, but I don't know how to deal with the remaining failed test test-312 😢

Look like the format check failed:

ERROR: "private::lint.black" exited with 1.

I changed the pre-commit hook to only lint staged files and should runs almost instantly for these cases now.

I can't figure out exactly what caused the code format check to fail 😢, I've used ruff to format related .py files.

That is because we use black not ruff 😆

Yes, I used to think that ruff was 100% compatible with the black standard 😣. After executing npm run format, the relevant lint tests have passed, but I don't know how to deal with the remaining failed test test-312 😢

No worry, the test-312 circleci container has been instable since the update to their v2 container. I started moving tests to github actions.